Non-Contention Based Low Latency Scheduling Request Transmission

ABSTRACT

Briefly, in accordance with one or more embodiments, an apparatus of a user equipment (UE) comprises circuitry to configure a scheduling request (SR) transmission based on a physical uplink control channel (PUCCH), and combine the scheduling request with a buffer status report (BSR). The UE transmits the combined SR and BSR in a single subframe to a network entity, receives uplink resource scheduling from the network entity in reply to the combined SR and BSR, and transmits uplink data to the network entity according to the uplink resource scheduling.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application claims priority under 35 U.S.C. 365(b) toInternational Application No. PCT/CN2015/079492 filed May 21, 2015(Docket No. P85635PCT-Z). Said Application No. PCT/CN2015/079492 ishereby incorporated herein by reference in its entirety.

BACKGROUND

In one or more embodiments, a network may operate in accordance with aThird Generation Partnership Project (3GPP) Long Term Evolution (LTE)standard or a Long Term Evolution Advanced (LTE-A). In such a network, ascheduling request (SR) may be used for user equipment (UE) to requestan uplink resource. The UE may send its SR in a non-contention basedmanner based on a physical uplink control channel (PUCCH). First, the UEsends its scheduling request (SR) to an evolved Node B (eNB) in thePUCCH. The UE waits for the eNB to send an uplink (UL) grant before theUE sends its buffer status report (BSR) to the eNB. In response, the eNBmay schedule the uplink resource for uplink data transmission for the UEbased on the received BSR wherein eNB sends the schedule at a next ULgrant. The UE may then transmit its UL data to eNB according to thescheduled resources. Such an arrangement may have high latency since theSR and the BSR are transmitted in different subframes, especially if theUE has a short buffer.

DESCRIPTION OF THE DRAWING FIGURES

Claimed subject matter is particularly pointed out and distinctlyclaimed in the concluding portion of the specification. However, suchsubject matter may be understood by reference to the following detaileddescription when read with the accompanying drawings in which:

FIG. 1 is a diagram of a network illustrating reduction of latency inthe scheduling request transmission in accordance with one or moreembodiments;

FIG. 2 is a diagram of the network of FIG. 1 in which a schedulingrequest and a buffer status report are sent together within a subframein accordance with one or more embodiments;

FIG. 3 is a diagram of the network in FIG. 1 in which a schedulingrequest and buffer status report group indicator are sent togetherwithin a subframe in accordance with one or more embodiments;

FIG. 4 is a block diagram of an information handling system capable oflatency reduction in the scheduling request transmission in accordancewith one or more embodiments;

FIG. 5 is an isometric view of an information handling system of FIG. 4that optionally may include a touch screen in accordance with one ormore embodiments; and

FIG. 6 is a diagram of example components of a wireless device inaccordance with one or more embodiments.

It will be appreciated that for simplicity and/or clarity ofillustration, elements illustrated in the figures have not necessarilybeen drawn to scale. For example, the dimensions of some of the elementsmay be exaggerated relative to other elements for clarity. Further, ifconsidered appropriate, reference numerals have been repeated among thefigures to indicate corresponding and/or analogous elements.

DETAILED DESCRIPTION

In the following detailed description, numerous specific details are setforth to provide a thorough understanding of claimed subject matter.However, it will be understood by those skilled in the art that claimedsubject matter may be practiced without these specific details. In otherinstances, well-known methods, procedures, components and/or circuitshave not been described in detail.

In the following description and/or claims, the terms coupled and/orconnected, along with their derivatives, may be used. In particularembodiments, connected may be used to indicate that two or more elementsare in direct physical and/or electrical contact with each other.Coupled may mean that two or more elements are in direct physical and/orelectrical contact. However, coupled may also mean that two or moreelements may not be in direct contact with each other, but yet may stillcooperate and/or interact with each other. For example, “coupled” maymean that two or more elements do not contact each other but areindirectly joined together via another element or intermediate elements.Finally, the terms “on,” “overlying,” and “over” may be used in thefollowing description and claims. “On,” “overlying,” and “over” may beused to indicate that two or more elements are in direct physicalcontact with each other. However, “over” may also mean that two or moreelements are not in direct contact with each other. For example, “over”may mean that one element is above another element but not contact eachother and may have another element or elements in between the twoelements. Furthermore, the term “and/or” may mean “and”, it may mean“or”, it may mean “exclusive-or”, it may mean “one”, it may mean “some,but not all”, it may mean “neither”, and/or it may mean “both”, althoughthe scope of claimed subject matter is not limited in this respect. Inthe following description and/or claims, the terms “comprise” and“include,” along with their derivatives, may be used and are intended assynonyms for each other.

Referring now to FIG. 1, a diagram of a network illustrating reductionof latency in the scheduling request transmission in accordance with oneor more embodiments will be discussed. As shown in FIG. 1, in one ormore embodiments network 100 may operate in accordance with a ThirdGeneration Partnership Project (3GPP) Long Term Evolution (LTE) standardor a Long Term Evolution Advanced (LTE-A), although the scope of theclaimed subject matter is not limited in this respect. UE 110 may sendthe SR and the BSR together within the same subframe, instead of indifferent subframes at operation 114 and operation 116 after UL grantoperation 116, by combining the SR and the BSR at procedure 124 so thatthe combined SR and BSR may be transmitted in a single operation in thesame subframe. In one or more embodiments, the combined SR and BSR maybe transmitted together based on an LTE non-contention based SRtransmission framework, so that the latency of BSR transmission and thecorresponding uplink grant procedure may be reduced. In such anarrangement, after receipt of a combined SR and BSR operation, combinedat procedure 124, eNB 112 may schedule UL resources at UL grantprocedure 120 to allow for UE 110 to transmit UL data at procedure 120.For example, the combined SR and BSR message may be transmitted based onPUCCH format 1 or PUCCH format 2, although the scope of the claimedsubject matter is not limited in these respects.

In one or more embodiments, combining the SR and the BSR into a singlemessage may reduce uplink data transmission latency for the UE 110,especially if UE 110 has a short data buffer, by eliminating procedure116 and procedure 118. The transmission of a combined SR and BSR messagemay be based on the PUCCH in a non-contention manner wherein UE 110 maybe configured with an SR transmission subframe period and an offsetdefining the subframe number for UE 110 to transmit its SR. The eNodeB110 may detect this combined SR and BSR transmission at the samesubframe to check whether an uplink resource is needed for the UE 110.In one embodiment, the BSR may comprise an 8-bit message which asdefined in 3GPP Technical Standard (TS) 36.321, and the SR may be a1-bit trigger, although the scope of the claimed subject matter is notlimited in these respects. A first approach to transmit the SR and theBSR within the same subframe is shown in and described with respect toFIG. 2, below.

Referring now to FIG. 2, a diagram of the network of FIG. 1 in which ascheduling request and a buffer status report are sent together within asubframe in accordance with one or more embodiments will be discussed.In one embodiment, a scheduling request (SR) for UE 110 may beconfigured to transmit in PUCCH format 2 way at the same PUCCH resourceas the periodical Channel State Information (CSI) feedback. The bufferstatus report (BSR) bits may be transmitted based on PUCCH format 2. Theconfigured SR subframe may be different from the periodical CSI feedbacksubframe. The UE 110 may feedback its periodical CSI when SRtransmission and periodical CSI feedback are transmitted in the samesubframe.

In some embodiments, the signal generation may be the same as describedin section 5.4.2 of 3GPP TS 36.211, where the input bits b(0), b(1), . .. , b(N−1) may be the BSR message, and N is the message bits number,which may be 8, as an example. In such embodiments, a procedure totransmit a combined SR and BSR could be as shown in FIG. 2. The combinedSR and BSR message may be transmitted from UE 110 to eNB 112 atprocedure 210. If eNB 112 decodes the combined SR and BSR messagecorrectly, eNB 112 may allocate a reasonable resource in uplink grant atprocedure 212 for the next uplink data transmission from UE 110 atprocedure 214. An alternative approach to transmit the SR and the BSRwithin the same subframe is shown in and described with respect to FIG.3, below.

Referring now to FIG. 3, a diagram of the network in FIG. 1 in which ascheduling request and buffer status report group indicator are senttogether within a subframe in accordance with one or more embodimentswill be discussed. In another embodiment, if UE 110 has a long buffer ormultiple Logical Channel Groups (LCGs), the BSR may be sent togetherwith SR, but the uplink packages transmission may not complete within asingle subframe. For such users, and exact BSR value associated with theSR does not have to be transmitted. If UE 110 has a short buffer whereinthe uplink packages transmission is able to be completed within a singlesubframe, enough Resource Blocks (RBs) may be scheduled so that the datamay be transmitted in a single roundtrip, and the transmission latencycould be reduced. As a result. Therefore, instead of transmitting anexact BSR, a BSR Group Indicator (BSRGI) may be sufficient to indicatewhether a long BSR or a short BSR is at the UE 110.

In such an arrangement, the BSR may be divided into M number of groups,wherein M may be, for example, 2, 3 or 4, and so on. The BSRGI may beused to indicate which BSR groups to which the current BSR belongs, andthe value of the BSRGI may be decided by a BSR group threshold. The BSRgroup threshold may depends on a power control factor of the UE 110,uplink CSI, and so on. The BSR group threshold may be configured by eNB112 via high layer messages, and the BSR group threshold may becell-specific or UE-specific. For example, the BSR may be divided intotwo groups, and the group threshold may be set to be T. If the value ofBSRGI is zero (0), the value of the BSRGI indicates current bufferlength of UE 110 is below K, where K is the maximum buffer size for BSRwhose value is equals to T. Otherwise, the buffer length of the UE 110is above K.

In one or more embodiments, the BSRGI may be transmitted based on PUCCHformat 1 or PUCCH format 2. For PUCCH format 1, the PUCCH signalgeneration may be based on 5.4.1 in 3GPP TS 36.211, and its DemodulationReference Signal (DMRS) generation may be based on section 5.5.2.2 of3GPP TS 36.211. In some embodiments, format 1b may be utilized for SRtransmission associated with acknowledgement or negative acknowledgment(ACK/NACK) transmission. One of the input bits b(0) or b(1) may indicatethe ACK/NACK state, and the other one of the input bits may indicate theBSRGI. If UE 110 has two codeword ACK/NACK feedback, an ACK/NACKbundling may be utilized to compress the two ACK/NACK bits into a singlebit if there is collision with SR transmission. Table 1, below, shows anexample of the symbol generation method.

TABLE 1 Example of d(0) Generation ACK/NACK BSRGI d(0) 0 0 1 0 1 −j  1 0j 1 1 −1 

In an alternative embodiment, a PUCCH format 1c may be utilized which tosupport four bits of transmission. Two of the input bits may indicatethe ACK/NACK state, and the other two bits may indicate the BSRGI. Insuch an embodiment, an example of symbol generation method may be 16Quadrature Amplitude Modulation (QAM) may be utilized for symbolgeneration, although the scope of the claimed subject matter is notlimited in this respect.

In embodiments where PUCCH format 2 is utilized, the PUCCH signalgeneration may be the same as described in section 5.4.1 of 3GPP TS36.211, while the BSRGI may be transmitted together with feedback CSI.For example BSRGI bits may be added at the tail of CSI bits. In such anexample, two tailed bits may be utilized, with an allocation as shown inTable 2, below.

TABLE 2 Examples of PUCCH format 2 Tailed Bits allocation Tailed BitsInformation 00 No SR is transmitted 01 BSRGI = 0 10 BSRGI = 1 11 BSRGI =2

An example for this procedure is shown in FIG. 3 wherein the combined SRand BSRGI is transmitted in procedure 310, the uplink resources may bescheduled in procedure 312, and the uplink data may be transmitted inprocedure 314. In procedure 314, the UE 110 does not transmit the BSR ifpadding is needed. Then after decoding message of procedure 314, eNB 112may recognize the UE 110 as having no additional data in its uplinktransmission buffer if a BSR is not received. Otherwise, eNB 112 mayconsider the UE 110 as having uplink data pending transmission, and atthe next schedule time, the UE 110 may transmit its exact BSR.

Referring now to FIG. 4, a block diagram of an information handlingsystem capable of latency reduction in the scheduling requesttransmission in accordance with one or more embodiments will bediscussed. Information handling system 400 of FIG. 4 may tangibly embodyany one or more of the network elements described herein, above,including for example the elements of network 100 with greater or fewercomponents depending on the hardware specifications of the particulardevice. In one embodiment, information handling system 400 may tangiblyembody an apparatus of a user equipment (UE) comprising circuitry toconfigure a scheduling request (SR) transmission based on a physicaluplink control channel (PUCCH), combine the scheduling request with abuffer status report (BSR), transmit the combined SR and BSR in a singlesubframe to a network entity, receive uplink resource scheduling fromthe network entity in reply to the combined SR and BSR, and transmituplink data to the network entity according to the uplink resourcescheduling. In another embodiment, information handling system 400 maytangibly embody an apparatus of a user equipment (UE) comprisingcircuitry to configure a scheduling request (SR) transmission based on aphysical uplink control channel (PUCCH), combine the scheduling requestwith a buffer status report group indicator (BSRGI), transmit thecombined SR and BSRGI in a single subframe to a network entity, receiveuplink resource scheduling from the network entity in reply to thecombined SR and BSRGI, and transmit uplink data to the network entityaccording to the uplink resource scheduling. Although informationhandling system 400 represents one example of several types of computingplatforms, information handling system 400 may include more or fewerelements and/or different arrangements of elements than shown in FIG. 8,and the scope of the claimed subject matter is not limited in theserespects.

In one or more embodiments, information handling system 400 may includean application processor 410 and a baseband processor 412. Applicationprocessor 410 may be utilized as a general-purpose processor to runapplications and the various subsystems for information handling system400. Application processor 410 may include a single core oralternatively may include multiple processing cores. One or more of thecores may comprise a digital signal processor or digital signalprocessing (DSP) core. Furthermore, application processor 410 mayinclude a graphics processor or coprocessor disposed on the same chip,or alternatively a graphics processor coupled to application processor410 may comprise a separate, discrete graphics chip. Applicationprocessor 410 may include on board memory such as cache memory, andfurther may be coupled to external memory devices such as synchronousdynamic random access memory (SDRAM) 414 for storing and/or executingapplications during operation, and NAND flash 416 for storingapplications and/or data even when information handling system 400 ispowered off. In one or more embodiments, instructions to operate orconfigure the information handling system 400 and/or any of itscomponents or subsystems to operate in a manner as described herein maybe stored on an article of manufacture comprising a non-transitorystorage medium. In one or more embodiments, the storage medium maycomprise any of the memory devices shown in and described herein,although the scope of the claimed subject matter is not limited in thisrespect. Baseband processor 412 may control the broadband radiofunctions for information handling system 800. Baseband processor 412may store code for controlling such broadband radio functions in a NORflash 418. Baseband processor 412 controls a wireless wide area network(WWAN) transceiver 420 which is used for modulating and/or demodulatingbroadband network signals, for example for communicating via a 3GPP LTEor LTE-Advanced network or the like.

In general, WWAN transceiver 420 may operate according to any one ormore of the following radio communication technologies and/or standardsincluding but not limited to: a Global System for Mobile Communications(GSM) radio communication technology, a General Packet Radio Service(GPRS) radio communication technology, an Enhanced Data Rates for GSMEvolution (EDGE) radio communication technology, and/or a ThirdGeneration Partnership Project (3GPP) radio communication technology,for example Universal Mobile Telecommunications System (UMTS), Freedomof Multimedia Access (FOMA), 3GPP Long Term Evolution (LTE), 3GPP LongTerm Evolution Advanced (LTE Advanced), Code division multiple access2000 (CDMA2000), Cellular Digital Packet Data (CDPD), Mobitex, ThirdGeneration (3G), Circuit Switched Data (CSD), High-SpeedCircuit-Switched Data (HSCSD), Universal Mobile TelecommunicationsSystem (Third Generation) (UMTS (3G)), Wideband Code Division MultipleAccess (Universal Mobile Telecommunications System) (W-CDMA (UMTS)),High Speed Packet Access (HSPA), High-Speed Downlink Packet Access(HSDPA), High-Speed Uplink Packet Access (HSUPA), High Speed PacketAccess Plus (HSPA+), Universal Mobile TelecommunicationsSystem-Time-Division Duplex (UMTS-TDD), Time Division-Code DivisionMultiple Access (TD-CDMA), Time Division-Synchronous Code DivisionMultiple Access (TD-CDMA), 3rd Generation Partnership Project Release 8(Pre-4th Generation) (3GPP Rel. 8 (Pre-4G)), 3GPP Rel. 9 (3rd GenerationPartnership Project Release 9), 3GPP Rel. 10 (3rd Generation PartnershipProject Release 10), 3GPP Rel. 11 (3rd Generation Partnership ProjectRelease 11), 3GPP Rel. 12 (3rd Generation Partnership Project Release12), 3GPP Rel. 13 (3rd Generation Partnership Project Release 12), 3GPPRel. 14 (3rd Generation Partnership Project Release 12), 3GPP LTE Extra,LTE Licensed-Assisted Access (LAA), UMTS Terrestrial Radio Access(UTRA), Evolved UMTS Terrestrial Radio Access (E-UTRA), Long TermEvolution Advanced (4th Generation) (LTE Advanced (4G)), cdmaOne (2G),Code division multiple access 2000 (Third generation) (CDMA2000 (3G)),Evolution-Data Optimized or Evolution-Data Only (EV-DO), Advanced MobilePhone System (1st Generation) (AMPS (1G)), Total Access CommunicationSystem/Extended Total Access Communication System (TACS/ETACS), DigitalAMPS (2nd Generation) (D-AMPS (2G)), Push-to-talk (PTT), MobileTelephone System (MTS), Improved Mobile Telephone System (IMTS),Advanced Mobile Telephone System (AMTS), OLT (Norwegian for OffentligLandmobil Telefoni, Public Land Mobile Telephony), MTD (Swedishabbreviation for Mobiltelefonisystem D, or Mobile telephony system D),Public Automated Land Mobile (Autotel/PALM), ARP (Finnish forAutoradiopuhelin, “car radio phone”), NMT (Nordic Mobile Telephony),High capacity version of NTT (Nippon Telegraph and Telephone) (Hicap),Cellular Digital Packet Data (CDPD), Mobitex, DataTAC, IntegratedDigital Enhanced Network (iDEN), Personal Digital Cellular (PDC),Circuit Switched Data (CSD), Personal Handy-phone System (PHS), WidebandIntegrated Digital Enhanced Network (WiDEN), iBurst, Unlicensed MobileAccess (UMA), also referred to as also referred to as 3GPP GenericAccess Network, or GAN standard), Zigbee, Bluetooth®, Wireless GigabitAlliance (WiGig) standard, millimeter wave (mmWave) standards in generalfor wireless systems operating at 10-90 GHz and above such as WiGig,IEEE 802.11ad, IEEE 802.11ay, and so on, and/or general telemetrytransceivers, and in general any type of RF circuit or RFI sensitivecircuit. It should be noted that such standards may evolve over time,and/or new standards may be promulgated, and the scope of the claimedsubject matter is not limited in this respect.

The WWAN transceiver 420 couples to one or more power amps 442respectively coupled to one or more antennas 424 for sending andreceiving radio-frequency signals via the WWAN broadband network. Thebaseband processor 412 also may control a wireless local area network(WLAN) transceiver 426 coupled to one or more suitable antennas 428 andwhich may be capable of communicating via a Wi-Fi, Bluetooth®, and/or anamplitude modulation (AM) or frequency modulation (FM) radio standardincluding an IEEE 802.11 a/b/g/n standard or the like. It should benoted that these are merely example implementations for applicationprocessor 410 and baseband processor 412, and the scope of the claimedsubject matter is not limited in these respects. For example, any one ormore of SDRAM 414, NAND flash 416 and/or NOR flash 418 may compriseother types of memory technology such as magnetic memory, chalcogenidememory, phase change memory, or ovonic memory, and the scope of theclaimed subject matter is not limited in this respect.

In one or more embodiments, application processor 410 may drive adisplay 430 for displaying various information or data, and may furtherreceive touch input from a user via a touch screen 432 for example via afinger or a stylus. An ambient light sensor 434 may be utilized todetect an amount of ambient light in which information handling system400 is operating, for example to control a brightness or contrast valuefor display 430 as a function of the intensity of ambient light detectedby ambient light sensor 434. One or more cameras 436 may be utilized tocapture images that are processed by application processor 410 and/or atleast temporarily stored in NAND flash 416. Furthermore, applicationprocessor may couple to a gyroscope 438, accelerometer 440, magnetometer442, audio coder/decoder (CODEC) 444, and/or global positioning system(GPS) controller 446 coupled to an appropriate GPS antenna 448, fordetection of various environmental properties including location,movement, and/or orientation of information handling system 400.Alternatively, controller 446 may comprise a Global Navigation SatelliteSystem (GNSS) controller. Audio CODEC 444 may be coupled to one or moreaudio ports 450 to provide microphone input and speaker outputs eithervia internal devices and/or via external devices coupled to informationhandling system via the audio ports 450, for example via a headphone andmicrophone jack. In addition, application processor 410 may couple toone or more input/output (I/O) transceivers 452 to couple to one or moreI/O ports 454 such as a universal serial bus (USB) port, ahigh-definition multimedia interface (HDMI) port, a serial port, and soon. Furthermore, one or more of the I/O transceivers 452 may couple toone or more memory slots 456 for optional removable memory such assecure digital (SD) card or a subscriber identity module (SIM) card,although the scope of the claimed subject matter is not limited in theserespects.

Referring now to FIG. 5, an isometric view of an information handlingsystem of FIG. 8 that optionally may include a touch screen inaccordance with one or more embodiments will be discussed. FIG. 5 showsan example implementation of information handling system 400 of FIG. 4tangibly embodied as a cellular telephone, smartphone, or tablet typedevice or the like. The information handling system 400 may comprise ahousing 510 having a display 430 which may include a touch screen 432for receiving tactile input control and commands via a finger 516 of auser and/or a via stylus 518 to control one or more applicationprocessors 410. The housing 510 may house one or more components ofinformation handling system 400, for example one or more applicationprocessors 410, one or more of SDRAM 414, NAND flash 416, NOR flash 418,baseband processor 412, and/or WWAN transceiver 420. The informationhandling system 400 further may optionally include a physical actuatorarea 520 which may comprise a keyboard or buttons for controllinginformation handling system via one or more buttons or switches. Theinformation handling system 400 may also include a memory port or slot456 for receiving non-volatile memory such as flash memory, for examplein the form of a secure digital (SD) card or a subscriber identitymodule (SIM) card. Optionally, the information handling system 400 mayfurther include one or more speakers and/or microphones 524 and aconnection port 454 for connecting the information handling system 400to another electronic device, dock, display, battery charger, and so on.In addition, information handling system 400 may include a headphone orspeaker jack 528 and one or more cameras 436 on one or more sides of thehousing 510. It should be noted that the information handling system 400of FIG. 5 may include more or fewer elements than shown, in variousarrangements, and the scope of the claimed subject matter is not limitedin this respect.

As used herein, the terms “circuit” or “circuitry” may refer to, be partof, or include an Application Specific Integrated Circuit (ASIC), anelectronic circuit, a processor (shared, dedicated, or group), and/ormemory (shared, dedicated, or group) that execute one or more softwareor firmware programs, a combinational logic circuit, and/or othersuitable hardware components that provide the described functionality.In some embodiments, the circuitry may be implemented in, or functionsassociated with the circuitry may be implemented by, one or moresoftware or firmware modules. In some embodiments, circuitry may includelogic, at least partially operable in hardware. Embodiments describedherein may be implemented into a system using any suitably configuredhardware and/or software.

Referring now to FIG. 6, example components of a wireless device such asUser Equipment (UE) device 110 in accordance with one or moreembodiments will be discussed. User equipment (UE) may correspond, forexample, to UE 110 of network 100, or alternatively to eNB 112 ofnetwork 100, although the scope of the claimed subject matter is notlimited in this respect. In some embodiments, UE device 600 may includeapplication circuitry 602, baseband circuitry 604, Radio Frequency (RF)circuitry 606, front-end module (FEM) circuitry 608 and one or moreantennas 610, coupled together at least as shown.

Application circuitry 602 may include one or more applicationprocessors. For example, application circuitry 602 may include circuitrysuch as, but not limited to, one or more single-core or multi-coreprocessors. The one or more processors may include any combination ofgeneral-purpose processors and dedicated processors, for examplegraphics processors, application processors, and so on. The processorsmay be coupled with and/or may include memory and/or storage and may beconfigured to execute instructions stored in the memory and/or storageto enable various applications and/or operating systems to run on thesystem.

Baseband circuitry 604 may include circuitry such as, but not limitedto, one or more single-core or multi-core processors. Baseband circuitry604 may include one or more baseband processors and/or control logic toprocess baseband signals received from a receive signal path of RFcircuitry 606 and to generate baseband signals for a transmit signalpath of the RF circuitry 606. Baseband processing circuitry 604 mayinterface with the application circuitry 602 for generation andprocessing of the baseband signals and for controlling operations of theRF circuitry 606. For example, in some embodiments, the basebandcircuitry 604 may include a second generation (2G) baseband processor604 a, third generation (3G) baseband processor 604 b, fourth generation(4G) baseband processor 604 c, and/or one or more other basebandprocessors 604 d for other existing generations, generations indevelopment or to be developed in the future, for example fifthgeneration (5G), sixth generation (6G), and so on. Baseband circuitry604, for example one or more of baseband processors 604 a through 604 d,may handle various radio control functions that enable communicationwith one or more radio networks via RF circuitry 606. The radio controlfunctions may include, but are not limited to, signal modulation and/ordemodulation, encoding and/or decoding, radio frequency shifting, and soon. In some embodiments, modulation and/or demodulation circuitry ofbaseband circuitry 604 may include Fast-Fourier Transform (FFT),precoding, and/or constellation mapping and/or demapping functionality.In some embodiments, encoding and/or decoding circuitry of basebandcircuitry 804 may include convolution, tail-biting convolution, turbo,Viterbi, and/or Low Density Parity Check (LDPC) encoder and/or decoderfunctionality. Embodiments of modulation and/or demodulation and encoderand/or decoder functionality are not limited to these examples and mayinclude other suitable functionality in other embodiments.

In some embodiments, baseband circuitry 604 may include elements of aprotocol stack such as, for example, elements of an evolved universalterrestrial radio access network (EUTRAN) protocol including, forexample, physical (PHY), media access control (MAC), radio link control(RLC), packet data convergence protocol (PDCP), and/or radio resourcecontrol (RRC) elements. Processor 604 e of the baseband circuitry 604may be configured to run elements of the protocol stack for signaling ofthe PHY, MAC, RLC, PDCP and/or RRC layers. In some embodiments, thebaseband circuitry may include one or more audio digital signalprocessors (DSP) 604 f. The one or more audio DSPs 604 f may includeelements for compression and/or decompression and/or echo cancellationand may include other suitable processing elements in other embodiments.Components of the baseband circuitry may be suitably combined in asingle chip, a single chipset, or disposed on a same circuit board insome embodiments. In some embodiments, some or all of the constituentcomponents of baseband circuitry 604 and application circuitry 602 maybe implemented together such as, for example, on a system on a chip(SOC).

In some embodiments, baseband circuitry 604 may provide forcommunication compatible with one or more radio technologies. Forexample, in some embodiments, baseband circuitry 604 may supportcommunication with an evolved universal terrestrial radio access network(EUTRAN) and/or other wireless metropolitan area networks (WMAN), awireless local area network (WLAN), a wireless personal area network(WPAN). Embodiments in which baseband circuitry 604 is configured tosupport radio communications of more than one wireless protocol may bereferred to as multi-mode baseband circuitry.

RF circuitry 606 may enable communication with wireless networks usingmodulated electromagnetic radiation through a non-solid medium. Invarious embodiments, RF circuitry 606 may include switches, filters,amplifiers, and so on, to facilitate the communication with the wirelessnetwork. RF circuitry 606 may include a receive signal path which mayinclude circuitry to down-convert RF signals received from FEM circuitry608 and provide baseband signals to baseband circuitry 604. RF circuitry606 may also include a transmit signal path which may include circuitryto up-convert baseband signals provided by the baseband circuitry 1004and provide RF output signals to FEM circuitry 1008 for transmission.

In some embodiments, RF circuitry 606 may include a receive signal pathand a transmit signal path. The receive signal path of RF circuitry 606may include mixer circuitry 606 a, amplifier circuitry 606 b and filtercircuitry 606 c. The transmit signal path of RF circuitry 606 mayinclude filter circuitry 606 c and mixer circuitry 606 a. RF circuitry606 may also include synthesizer circuitry 606 d for synthesizing afrequency for use by the mixer circuitry 606 a of the receive signalpath and the transmit signal path. In some embodiments, the mixercircuitry 606 a of the receive signal path may be configured todown-convert RF signals received from FEM circuitry 608 based on thesynthesized frequency provided by synthesizer circuitry 606 d. Amplifiercircuitry 606 b may be configured to amplify the down-converted signalsand the filter circuitry 606 c may be a low-pass filter (LPF) orband-pass filter (BPF) configured to remove unwanted signals from thedown-converted signals to generate output baseband signals. Outputbaseband signals may be provided to baseband circuitry 604 for furtherprocessing. In some embodiments, the output baseband signals may bezero-frequency baseband signals, although this is not a requirement. Insome embodiments, mixer circuitry 606 a of the receive signal path maycomprise passive mixers, although the scope of the embodiments is notlimited in this respect.

In some embodiments, mixer circuitry 606 a of the transmit signal pathmay be configured to up-convert input baseband signals based on thesynthesized frequency provided by synthesizer circuitry 606 d togenerate RF output signals for FEM circuitry 608. The baseband signalsmay be provided by the baseband circuitry 604 and may be filtered byfilter circuitry 606 c. Filter circuitry 606 c may include a low-passfilter (LPF), although the scope of the embodiments is not limited inthis respect.

In some embodiments, mixer circuitry 606 a of the receive signal pathand the mixer circuitry 606 a of the transmit signal path may includetwo or more mixers and may be arranged for quadrature down conversionand/or up conversion respectively. In some embodiments, mixer circuitry606 a of the receive signal path and the mixer circuitry 606 a of thetransmit signal path may include two or more mixers and may be arrangedfor image rejection, for example Hartley image rejection. In someembodiments, mixer circuitry 606 a of the receive signal path and themixer circuitry 606 a may be arranged for direct down conversion and/ordirect up conversion, respectively. In some embodiments, mixer circuitry606 a of the receive signal path and mixer circuitry 606 a of thetransmit signal path may be configured for super-heterodyne operation.

In some embodiments, the output baseband signals and the input basebandsignals may be analog baseband signals, although the scope of theembodiments is not limited in this respect. In some alternateembodiments, the output baseband signals and the input baseband signalsmay be digital baseband signals. In these alternate embodiments, RFcircuitry 1006 may include analog-to-digital converter (ADC) anddigital-to-analog converter (DAC) circuitry, and baseband circuitry 604may include a digital baseband interface to communicate with RFcircuitry 606. In some dual-mode embodiments, separate radio integratedcircuit (IC) circuitry may be provided for processing signals for one ormore spectra, although the scope of the embodiments is not limited inthis respect.

In some embodiments, synthesizer circuitry 606 d may be a fractional-Nsynthesizer or a fractional N/N+1 synthesizer, although the scope of theembodiments is not limited in this respect as other types of frequencysynthesizers may be suitable. For example, synthesizer circuitry 606 dmay be a delta-sigma synthesizer, a frequency multiplier, or asynthesizer comprising a phase-locked loop with a frequency divider.

Synthesizer circuitry 606 d may be configured to synthesize an outputfrequency for use by mixer circuitry 606 a of RF circuitry 1006 based ona frequency input and a divider control input. In some embodiments,synthesizer circuitry 606 d may be a fractional N/N+1 synthesizer.

In some embodiments, frequency input may be provided by a voltagecontrolled oscillator (VCO), although that is not a requirement. Dividercontrol input may be provided by either baseband circuitry 604 orapplications processor 602 depending on the desired output frequency. Insome embodiments, a divider control input (e.g., N) may be determinedfrom a look-up table based on a channel indicated by applicationsprocessor 602.

Synthesizer circuitry 606 d of RF circuitry 1006 may include a divider,a delay-locked loop (DLL), a multiplexer and a phase accumulator. Insome embodiments, the divider may be a dual modulus divider (DMD) andthe phase accumulator may be a digital phase accumulator (DPA). In someembodiments, the DMD may be configured to divide the input signal byeither N or N+1, for example based on a carry out, to provide afractional division ratio. In some example embodiments, the DLL mayinclude a set of cascaded, tunable, delay elements, a phase detector, acharge pump and a D-type flip-flop. In these embodiments, the delayelements may be configured to break a VCO period up into Nd equalpackets of phase, where Nd is the number of delay elements in the delayline. In this way, the DLL provides negative feedback to help ensurethat the total delay through the delay line is one VCO cycle.

In some embodiments, synthesizer circuitry 606 d may be configured togenerate a carrier frequency as the output frequency, while in otherembodiments, the output frequency may be a multiple of the carrierfrequency, for example twice the carrier frequency, four times thecarrier frequency, and so on, and used in conjunction with quadraturegenerator and divider circuitry to generate multiple signals at thecarrier frequency with multiple different phases with respect to eachother. In some embodiments, the output frequency may be a localoscillator (LO) frequency (fLO). In some embodiments, RF circuitry 1006may include an in-phase and quadrature (IQ) and/or polar converter.

FEM circuitry 608 may include a receive signal path which may includecircuitry configured to operate on RF signals received from one or moreantennas 610, amplify the received signals and provide the amplifiedversions of the received signals to the RF circuitry 606 for furtherprocessing. FEM circuitry 608 may also include a transmit signal pathwhich may include circuitry configured to amplify signals fortransmission provided by RF circuitry 606 for transmission by one ormore of the one or more antennas 610.

In some embodiments, FEM circuitry 608 may include a transmit/receive(TX/RX) switch to switch between transmit mode and receive modeoperation. FEM circuitry 608 may include a receive signal path and atransmit signal path. The receive signal path of FEM circuitry 608 mayinclude a low-noise amplifier (LNA) to amplify received RF signals andto provide the amplified received RF signals as an output, for exampleto RF circuitry 606. The transmit signal path of FEM circuitry 608 mayinclude a power amplifier (PA) to amplify input RF signals, for exampleprovided by RF circuitry 606, and one or more filters to generate RFsignals for subsequent transmission, for example by one or more ofantennas 610. In some embodiments, UE device 600 may include additionalelements such as, for example, memory and/or storage, display, camera,sensor, and/or input/output (I/O) interface, although the scope of theclaimed subject matter is not limited in this respect.

The following are example implementations of the subject matterdescribed herein. It should be noted that any of the examples and thevariations thereof described herein may be used in any permutation orcombination of any other one or more examples or variations, althoughthe scope of the claimed subject matter is not limited in theserespects. In example one, an apparatus of a user equipment (UE) maycomprise circuitry to configure a scheduling request (SR) transmissionbased on a physical uplink control channel (PUCCH), combine thescheduling request with a buffer status report (BSR), transmit thecombined SR and BSR in a single subframe to a network entity, receiveuplink resource scheduling from the network entity in reply to thecombined SR and BSR, and transmit uplink data to the network entityaccording to the uplink resource scheduling. In example two, the subjectmatter of example one or any of the examples described herein furthermay comprise an apparatus, wherein the PUCCH comprises PUCCH format 1,PUCCH format 1b, PUCCH format 2, or PUCCH format 3, or a combinationthereof. In example three, the subject matter of example one or any ofthe examples described herein further may comprise radio-frequencycircuitry to transmit a combined SR and BSR periodically. In examplefour, the subject matter of example one or any of the examples describedherein further may comprise circuitry to transmit the BSR as a payloadof PUCCH format 2 or PUCCH format 3. In example five, the subject matterof example one or any of the examples described herein further maycomprise circuitry to transmit a channel state indicator (CSI) or anacknowledgement/negative acknowledgement (ACK/NACK) without transmittingthe combined SR and BSR if the combined SR and BSR transmission collideswith a CSI transmission or an ACK/NACK transmission in a same PUCCHresource. In example six, the subject matter of example one or any ofthe examples described herein further may comprise an apparatus, whereinone bit of the payload indicates an ACK/NACK and a discontinuoustransmission (DTX) state, and another bit of the payload indicates abuffer status report group indicator (BSRGI). In example seven, thesubject matter of example one or any of the examples described hereinfurther may comprise, an apparatus wherein the BSR is divided into twoor more groups, and a threshold is configured by radio resource control(RRC) signaling or as defined by a Third Generation Partnership Project(3GPP) standard.

In example eight, an apparatus of a user equipment (UE) may comprisecircuitry to configure a scheduling request (SR) transmission based on aphysical uplink control channel (PUCCH), combine the scheduling requestwith a buffer status report group indicator (BSRGI), transmit thecombined SR and BSRGI in a single subframe to a network entity, receiveuplink resource scheduling from the network entity in reply to thecombined SR and BSRGI, and transmit uplink data to the network entityaccording to the uplink resource scheduling. In example nine, thesubject matter of example eight or any of the examples described hereinfurther may comprise circuitry to transmit the combined SR and BSRGImessage based on PUCCH format 2. In example ten, the subject matter ofexample eight or any of the examples described herein further maycomprise an apparatus, wherein the BSRGI comprises one bit or two bitsat an end of a PUCCH format 2 payload. In example eleven, the subjectmatter of example eight or any of the examples described herein furthermay comprise circuitry to transmit the combined SR and BSRGI messagetransmitted with a periodic channel state indicator (CSI). In exampletwelve, the subject matter of example eight or any of the examplesdescribed herein further may comprise an apparatus wherein the SR is nottransmitted if bits representing the BSRGI are all zeros.

In example thirteen, one or more computer-readable media may haveinstructions stored thereon that, if executed by user equipment (UE),result in configuring a scheduling request (SR) transmission based on aphysical uplink control channel (PUCCH), combining the schedulingrequest with a buffer status report (BSR), transmitting the combined SRand BSR in a single subframe to a network entity, receiving uplinkresource scheduling from the network entity in reply to the combined SRand BSR, and transmit uplink data to the network entity according to theuplink resource scheduling. In example fourteen, the subject matter ofexample thirteen or any of the examples described herein further maycomprise one or more computer-readable media, wherein the PUCCHcomprises PUCCH format 1, PUCCH format 1b, PUCCH format 2, or PUCCHformat 3, or a combination thereof. In example fifteen, the subjectmatter of example thirteen or any of the examples described hereinfurther may comprise one or more computer-readable media, wherein theinstructions, if executed by the UE, result in transmitting a combinedSR and BSR periodically. In example sixteen, the subject matter ofexample thirteen or any of the examples described herein further maycomprise one or more computer-readable media, wherein the instructions,if executed by the UE, result in transmitting the BSR as a payload ofPUCCH format 2 or PUCCH format 3. In example seventeen, the subjectmatter of example thirteen or any of the examples described hereinfurther may comprise one or more computer-readable media, wherein theinstructions, if executed by the UE, result in transmitting a channelstate indicator (CSI) or an acknowledgement/negative acknowledgement(ACK/NACK) without transmitting the combined SR and BSR if the combinedSR and BSR transmission collides with a CSI transmission or an ACK/NACKtransmission in a same PUCCH resource. In example eighteen, the subjectmatter of example thirteen or any of the examples described hereinfurther may comprise one or more computer-readable media, wherein onebit of the payload indicates an ACK/NACK and a discontinuoustransmission (DTX) state, and another bit of the payload indicates abuffer status report group indicator (BSRGI). In example nineteen, thesubject matter of example thirteen or any of the examples describedherein further may comprise one or more computer-readable media, whereinthe BSR is divided into two or more groups, and a threshold isconfigured by radio resource control (RRC) signaling as defined by aThird Generation Partnership Project (3GPP) standard.

In example twenty, one or more computer-readable media may haveinstructions stored thereon that, if executed by user equipment (UE),result in configuring a scheduling request (SR) transmission based on aphysical uplink control channel (PUCCH), combining the schedulingrequest with a buffer status report group indicator (BSRGI),transmitting the combined SR and BSRGI in a single subframe to a networkentity, receiving uplink resource scheduling from the network entity inreply to the combined SR and BSRGI, and transmitting uplink data to thenetwork entity according to the uplink resource scheduling. In exampletwenty-one, the subject matter of example twenty or any of the examplesdescribed herein further may comprise one or more computer-readablemedia, wherein the instructions, if executed by the UE, result intransmitting the combined SR and BSRGI message based on PUCCH format 2.In example twenty-two, the subject matter of example thirteen or any ofthe examples described herein further may comprise one or morecomputer-readable media, wherein the BSRGI comprises one bit or two bitsat an end of a PUCCH format 2 payload. In example twenty-three, thesubject matter of example thirteen or any of the examples describedherein further may comprise one or more computer-readable media, whereinthe instructions, if executed by the UE, result in transmitting thecombined SR and BSRGI message transmitted with a periodic channel stateindicator (CSI). In example twenty-four, the subject matter of examplethirteen or any of the examples described herein further may compriseone or more computer-readable media, wherein the SR is not transmittedif bits representing the BSRGI are all zeros.

Although the claimed subject matter has been described with a certaindegree of particularity, it should be recognized that elements thereofmay be altered by persons skilled in the art without departing from thespirit and/or scope of claimed subject matter. It is believed that thesubject matter pertaining to non-contention based low latency schedulingrequest transmission and many of its attendant utilities will beunderstood by the forgoing description, and it will be apparent thatvarious changes may be made in the form, construction and/or arrangementof the components thereof without departing from the scope and/or spiritof the claimed subject matter or without sacrificing all of its materialadvantages, the form herein before described being merely an explanatoryembodiment thereof, and/or further without providing substantial changethereto. It is the intention of the claims to encompass and/or includesuch changes.

1-24. (canceled)
 25. An apparatus of a user equipment (UE) comprisingcircuitry to: configure a scheduling request (SR) transmission based ona physical uplink control channel (PUCCH); combine the schedulingrequest with a buffer status report (BSR); transmit the combined SR andBSR in a single subframe to a network entity; receive uplink resourcescheduling from the network entity in reply to the combined SR and BSR;and transmit uplink data to the network entity according to the uplinkresource scheduling.
 26. The apparatus as claimed in claim 25, whereinthe PUCCH comprises PUCCH format 1, PUCCH format 1b, PUCCH format 2, orPUCCH format 3, or a combination thereof.
 27. The apparatus as claimedin claim 25, comprising radio-frequency circuitry to transmit a combinedSR and BSR periodically.
 28. The apparatus as claimed in claim 25,comprising radio-frequency circuitry to transmit the BSR as a payload ofPUCCH format 2 or PUCCH format
 3. 29. The apparatus as claimed in claim25, comprising radio-frequency circuitry to: transmit a channel stateindicator (CSI) or an acknowledgement/negative acknowledgement(ACK/NACK) without transmitting the combined SR and BSR if the combinedSR and BSR transmission collides with a CSI transmission or an ACK/NACKtransmission in a same PUCCH resource.
 30. The apparatus as claimed inclaim 29, wherein one bit of the payload indicates an ACK/NACK and adiscontinuous transmission (DTX) state, and another bit of the payloadindicates a buffer status report group indicator (BSRGI).
 31. Theapparatus as claimed in claim 25, wherein the BSR is divided into two ormore groups, and a threshold is configured by radio resource control(RRC) signaling or as defined by a Third Generation Partnership Project(3GPP) standard.
 32. An apparatus of a user equipment (UE) comprisingcircuitry to: configure a scheduling request (SR) transmission based ona physical uplink control channel (PUCCH); combine the schedulingrequest with a buffer status report group indicator (BSRGI); transmitthe combined SR and BSRGI in a single subframe to a network entity;receive uplink resource scheduling from the network entity in reply tothe combined SR and BSRGI; and transmit uplink data to the networkentity according to the uplink resource scheduling.
 33. The apparatus asclaimed in 32, comprising radio-frequency circuitry to transmit thecombined SR and BSRGI message based on PUCCH format
 2. 34. The apparatusas claimed in claim 33, wherein the BSRGI comprises one bit or two bitsat an end of a PUCCH format 2 payload.
 35. The apparatus as claimed inclaim 32, comprising radio-frequency circuitry to transmit the combinedSR and BSRGI message transmitted with a periodic channel state indicator(CSI).
 36. The apparatus as claimed in claim 32, wherein the SR is nottransmitted if bits representing the BSRGI are all zeros.
 37. One ormore computer-readable media having instructions stored thereon that, ifexecuted by user equipment (UE), result in: configuring a schedulingrequest (SR) transmission based on a physical uplink control channel(PUCCH); combining the scheduling request with a buffer status report(BSR); transmitting the combined SR and BSR in a single subframe to anetwork entity; receiving uplink resource scheduling from the networkentity in reply to the combined SR and BSR; and transmit uplink data tothe network entity according to the uplink resource scheduling.
 38. Theone or more computer-readable media as claimed in claim 37, wherein thePUCCH comprises PUCCH format 1, PUCCH format 1b, PUCCH format 2, orPUCCH format 3, or a combination thereof.
 39. The one or morecomputer-readable media as claimed in claim 37, wherein theinstructions, if executed by the UE, result in transmitting a combinedSR and BSR periodically.
 40. The one or more computer-readable media asclaimed in claim 37, wherein the instructions, if executed by the UE,result in transmitting the BSR as a payload of PUCCH format 2 or PUCCHformat
 3. 41. The one or more non-transitory computer-readable media asclaimed in claim 13, wherein the instructions, if executed by the UE,result in: transmitting a channel state indicator (CSI) or anacknowledgement/negative acknowledgement (ACK/NACK) without transmittingthe combined SR and BSR if the combined SR and BSR transmission collideswith a CSI transmission or an ACK/NACK transmission in a same PUCCHresource.
 42. The one or more non-transitory computer-readable media asclaimed in claim 41, wherein one bit of the payload indicates anACK/NACK and a discontinuous transmission (DTX) state, and another bitof the payload indicates a buffer status report group indicator (BSRGI).43. The one or more non-transitory computer-readable media as claimed inclaim 37, wherein the BSR is divided into two or more groups, and athreshold is configured by radio resource control (RRC) signaling asdefined by a Third Generation Partnership Project (3GPP) standard. 44.One or more non-transitory computer-readable media having instructionsstored thereon that, if executed by user equipment (UE), result in:configuring a scheduling request (SR) transmission based on a physicaluplink control channel (PUCCH); combining the scheduling request with abuffer status report group indicator (BSRGI); transmitting the combinedSR and BSRGI in a single subframe to a network entity; receiving uplinkresource scheduling from the network entity in reply to the combined SRand BSRGI; and transmitting uplink data to the network entity accordingto the uplink resource scheduling.
 45. The one or more non-transitorycomputer-readable media as claimed in claim 44, wherein theinstructions, if executed by the UE, result in transmitting the combinedSR and BSRGI message based on PUCCH format
 2. 46. The one or morenon-transitory computer-readable media as claimed in claim 45, whereinthe BSRGI comprises one bit or two bits at an end of a PUCCH format 2payload.
 47. The one or more non-transitory computer-readable media asclaimed in claim 44, wherein the instructions, if executed by the UE,result in transmitting the combined SR and BSRGI message transmittedwith a periodic channel state indicator (CSI).
 48. The one or morenon-transitory computer-readable media as claimed in claim 44, whereinthe SR is not transmitted if bits representing the BSRGI are all zeros.